Add a reset counter api to set the time back to 0.

Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>

Introduce a counter set value api to set the ticks for 32b and 64b.

Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>

This introduces apis for input capture on the STM32. This is something
agnostic enough that is seen on other vendors such as Atmel's SAM line
and others.

A use case for this would be time stamping a rising and/or falling edge
where precision and lack of jitter is important. The only way to currently
do this in zephyr is to set up a GPIO interrupt and then read the counter
or kernel time... but this can have limitations of software such as the
processor may have a lot going on and can be subject to interrupt
latencies. Having a hardware 'latch' done of the rising and/or falling
edge with respect to a timer can eliminate these imprecisions.

How this is to be used, is that an application is to call
`capture_callback_set` with the configuration of the channel number, flags
(such as falling, rising, or both edges), and then a callback function.
Then the `capture_enable` function is to be called to enable this. The
callback has the timestamp of the edge in ticks and the edge that it
captured (rising or falling).

Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>

Some counters, such as those that use fractional adders, tick at
resolutions greater than 4294967295Hz. This changes the freq in the common
info to a uint64_t. This retains the existing `counter_get_freq` function
which will still return a 32bit value. This also adds a
`counter_get_freq_64` function to get a 64bit value for the frequency.

Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>

Add inline helper functions for converting ticks to nanoseconds.

Also implement an inline helper for converting microseconds or
nanoseconds with a 64bit tick value.

Signed-off-by: Ryan McClelland <ryanmcclelland@meta.com>